Repository navigation
feat(web): a narrow window shows the rail only beside the open left panel - #216
Conversation
|
Supervisor: read on head
Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread mcp:57942b76-ee73-4e62-b152-1b92ea2a0812 |
|
Merge hold: this PR must not reach Order agreed for the release: The code is unchanged and still ready for review; only the merge waits. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread b2963c0a-0588-4dde-8ece-390971647afc |
|
@immakermatty Předávám Vám odpovědnost za PR: podle dohodnutého pořadí se nesmí sloučit před tagem — Pablo |
agentrozjedemeai
left a comment
There was a problem hiding this comment.
Blocking:
- Restore keyboard and screen-reader access to the Lazurio rail at widths below 768 px. With the panel closed,
visibility: hiddenremoves the rail from navigation; with it open, the modal sheet traps focus and gives the railaria-hidden(as the PR also notes). Previously the rail was available when the panel was closed. Its navigation, including the Environment and account controls, is now unreachable in both states. Make the visible controls accessible and verify both input modes. - Add the repository-required before/after images and a short video for the changed layout and animation to this PR. The measurements in the description do not show the visual result or motion.
Non-blocking: The release contract tests pass (52/52) and changed-file formatting passes. I could not verify the integrated Lazurio shell in a real client: this checkout's dev server does not supply the Lazurio shell, and the repository's built-in browser panel is unavailable here. Two CI jobs are still pending.
Order and migrations: Tag v0.1.9-lazurio.1 before merging this PR; #214 and this PR then go into the same 0.1.9-lazurio.2 preview as recorded in #216 (comment).
— Pablo
|
Thanks. Both blocking points are addressed in 92882a11b0. 1. Keyboard and screen-reader access. You were right. While the open panel (T3's modal sheet) traps focus and marks the page outside it With the panel closed, the rail is deliberately not shown. The requested design is that the conversation takes the full width and the rail belongs to the open panel. Keyboard users reach the rail the same way as everyone else: the panel toggle (Ctrl+B, or the toggle button in the header) opens the panel, and the rail is the first stop inside it. Every rail control, Environment and account included, is reachable in that state. A side effect showed up in the captures and is fixed: while the rail is not 2. Evidence. The description now has before/after captures at 390, 700 and 1440 in both states, two keyboard captures, and a recording of opening and closing at 390. They come from the live 0.1.9 preview with exactly this CSS and script injected. Captures on the real build follow with the Two behaviours are the same before and after this PR, so I left them out of scope; both are noted in the description. Ctrl/⌘+Shift+E is T3's The merge hold is unchanged: merge only after Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread b2963c0a-0588-4dde-8ece-390971647afc |
agentrozjedemeai
left a comment
There was a problem hiding this comment.
Blocking:
apps/web/index.html:725: When the narrow panel is closed,display: nonehides the rail but it remains the shell’s keyboard shortcut target. If ⌘/Ctrl+Shift+E reaches the shell (for example after the conflicting T3 binding is changed),openJump()callsshowModal()on a dialog inside the hidden rail. The modal opens with no visible box while focus outside it is blocked; the user cannot see or use the Environment jump. Preserve a visible, usable jump when the rail is hidden and add a behavioral regression check for the closed-panel case. A browser reproduction of a modal inside adisplay: noneshadow host confirmed the invisible modal and blocked outside focus. The usual Chat shortcut conflict noted in the PR limits when this path is reached but does not remove it.
Non-blocking: node --test scripts/lazurio-release-contract.test.mjs passed (52/52); vp run check:changed passed. The real application and physical touch device were not independently exercised; the PR supplies injected-preview evidence. CI was still running at review time.
Order and migrations: Do not merge before v0.1.9-lazurio.1 is tagged; #214 and this change are planned for the same 0.1.9-lazurio.2 preview.
Agent: OpenMausBot Steward 2 · assignment fdfe07de-1c53-4c3e-a243-e08580c9972f
— Pablo
|
Agreed, and fixed in 07e2c7d6b2. The path is real even though Chat rarely reaches it today: T3 takes Ctrl/⌘+Shift+E outside the terminal, and the terminal takes it too.
The merge hold is unchanged: merge only after Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread b2963c0a-0588-4dde-8ece-390971647afc |
agentrozjedemeai
left a comment
There was a problem hiding this comment.
Approved. The earlier accessibility and hidden-jump findings are addressed in the implementation and regression coverage; the PR now includes before/after captures and video.
Non-blocking: The release contract tests passed (52/52), changed-file formatting and lint passed, and web typecheck passed. I inspected the supplied narrow-panel capture; I did not independently exercise the integrated shell or run the new browser test. The author reports browser coverage and a passing check:changed; GitHub CI is still running.
Order and migrations: Tag v0.1.9-lazurio.1 before merging; #214 and this PR are planned for the same v0.1.9-lazurio.2 preview.
Agent: OpenMausBot Steward 1 · assignment 365bcba0-663b-47ec-bbaa-087823bfc784
— Pablo
|
New in b5e8a837ba, added here rather than in a separate PR. This PR needs a rebase and a fresh review after The right panel takes the whole width in a narrow window. Below 768 px with the shell present,
The merge hold is unchanged: merge only after Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread b2963c0a-0588-4dde-8ece-390971647afc |
agentrozjedemeai
left a comment
There was a problem hiding this comment.
Approved. The earlier accessibility and hidden-jump findings were addressed in the previously reviewed changes; the added right-panel rule matches the current sheet uses and the supplied visual evidence.
Non-blocking: The release contract tests pass (52/52), changed-file formatting and lint pass, and web typecheck passes. I did not independently run the browser test or exercise the integrated shell; the PR supplies injected-preview evidence. GitHub CI is still queued.
Order and migrations: Tag v0.1.9-lazurio.1 before merging; #214 and this PR are planned for the same 0.1.9-lazurio.2 preview: #216 (comment).
Agent: OpenMausBot Steward 9 · assignment 1e91f5f3-87a0-4b2b-959f-6fc3d419674a
— Pablo
…anel Below 768 px, where T3's left panel is a sheet, the conversation takes the whole width and the Lazurio rail is hidden. Opening the left panel brings the rail in beside it: the panel moves aside by the rail's width and the rail slides in with it (none with reduced motion). The wide layout is unchanged. CSS only, in index.html; the contract test guards the rule and T3's breakpoint. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread b2963c0a-0588-4dde-8ece-390971647afc Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…eyboard and screen readers T3's left panel in a narrow window is a modal sheet: it keeps the focus inside and marks the rest of the page aria-hidden, so a rail beside it was out of reach for the keyboard and screen readers. A short script in index.html's head moves the rail into the panel, as its first child, while the panel is on the page, and back before #root once it is gone, where it stays the jump's target. The panel leaves room for it. The sidebar wrapper stays contained while the rail is not #root's sibling, so T3's fixed controls stay below the panel. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread b2963c0a-0588-4dde-8ece-390971647afc Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ail is hidden With the narrow panel closed the rail is hidden, yet it stays the target of the Environment jump. A dialog opened inside a hidden host is invisible and blocks the page. The rail is now shown while a dialog of its own is open, and already when the jump's key comes, before the shell takes it, so the jump's search gets the focus as it opens; once the key has passed, the rail settles and hides again when the app took the key. A browser test drives T3's real sidebar with index.html's style and script: hidden beside the conversation, inside the open panel, the jump visible and typable, and hidden when the app takes the key. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread b2963c0a-0588-4dde-8ece-390971647afc Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Below 768 px T3's right panel is a sheet of min(88vw, 24rem), with a sliver of the conversation and the rail beside it. With the Lazurio shell it now takes the whole width, like the open left panel; its own toggle or Escape closes it, back to the conversation. CSS only, in index.html's narrow block; the wide layout and T3 outside Lazurio keep upstream's width. The browser test renders the real RightPanelSheet at 390 and 900 px, with and without the shell. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread b2963c0a-0588-4dde-8ece-390971647afc Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
b5e8a83 to
ae9d237
Compare
agentrozjedemeai
left a comment
There was a problem hiding this comment.
Approved. The earlier accessibility and hidden-jump findings are addressed; the right-panel rule matches the current sheet uses.
Non-blocking: The release contract passes locally (52/52). CI on this head passes formatting, lint, typechecking and the six narrow-rail browser tests. I did not independently exercise the integrated shell in a real client; the PR supplies injected-preview evidence, and the actual preview build remains to be checked.
Order and migrations: Tag v0.1.9-lazurio.1 before merging; #214 and this PR are planned for the same 0.1.9-lazurio.2 preview: #216 (comment).
Agent: environment unknown · bot 893f8471-aa66-4db7-864e-7791c0db5ab0
— Pablo
…anel Below 768 px, where T3's left panel is a sheet, the conversation takes the whole width and the Lazurio rail is hidden. Opening the left panel moves the rail into the open panel as its first element, so keyboard and screen readers reach it inside the modal sheet; closing it puts the rail back before #root, where the jump (Mod+Shift+E) still opens visible and ready to type. The wide layout is unchanged. CSS and a short script in index.html; the contract test guards the rule and T3's breakpoint. On v0.1.10 T3 keeps the closed sheet mounted with the hidden attribute, so its thread shortcuts keep working (pingdotgg#23568). The rail goes into the panel only while it is not hidden, and the script watches hidden as well as aria-hidden. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Below 768 px T3's right panel is a sheet of min(88vw, 24rem), with a sliver of the conversation and the rail beside it. With the Lazurio shell it now takes the whole width, like the open left panel; its own toggle or Escape closes it, back to the conversation. CSS only, in index.html's narrow block; the wide layout and T3 outside Lazurio keep upstream's width. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The distribution's files on the new base, upstream T3 Code v0.1.10 (7d32075), last in the stack: CI, the CLI archive, release and upstream watch workflows, the image, the issue form, README, SECURITY.md, the runbook, the overlay spec, the contract test, the release version check and the rebuild's skill. They are main's files, made current for v0.1.10 (#213). Main's base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9 below are kept from the earlier rebuilds. On v0.1.4: - The allowlist gains five files: chat/ThreadServersPanel.tsx, where a click on a thread's server opens it in the Environment browser (row 9); sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts, for the per-server target and the continuation gate of v0.1.4's update dialog (row 4); upstream's installer test install.test.ts, whose fixture needs upstream's repository named (row 4); and cli/environment.ts, whose settings take Buddy's linked-Environments guard (row 25). ServerEnvironment.test.ts keeps the update-check guard (row 4). - The contract test's pins follow the seams that moved: upstream deleted LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column head is pinned in the thread sidebar only; the sidebar reads useDelegatedUnderParent before the managed check; the empty panel and Nová karta carry the workspace focus default; the MCP session issue calls mcpClientScopes directly; an agent command's scope drops the session's web origin so its thread links stay t3-thread:// links; the Buddy composer hook takes only the environment, since v0.1.4's resting composer has no strip of its own; the timeline has no paint-only gate (pingdotgg#25787); the steer guard returns through stopRunForQueuedCommand and also holds a delegated task's completion wake; the Servers panel's click opens the Environment browser; and Buddy's server settings layer turns linked Environments off. - Rows 30, 32 and 33, which main carried as commits after row 31, now sit in their rows; row 28's addenda are back in rows 7, 23 and 25. Upstream renamed the lint rule react-effect-budget to t3code/no-unreasoned-state-sync (pingdotgg#26161). - The skill's inventory groups cover rows 23 to 33. - Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name only fictional people and hosts (Alena, Bob, example-person, vm-0x.example.lazurio.io), since the repository is public. On v0.1.5: - CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy. - The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so lazurio-cli-archives.yml installs patchelf before the build, the way upstream's release-desktop.yml does; the contract test pins the order. - useUpdateEverything.ts leaves the allowlist: row 4 now keeps a server's advertised release out of waitForNpm in updateEverything.logic.ts (pingdotgg#26917), and the contract test pins that seam there. The fixed test gate is unchanged, and every gated path exists at v0.1.5. - The contract test's pairing pins follow the constants that knip made module-private (upstream's pre-commit hook runs knip:check since pingdotgg#26167). - The runbook's Overlay table describes every row on v0.1.5, the Cílový stack names each row's new commit, the swap step names the workflows to disable after the swap from the v0.1.3 base (agent-context-budget.yml, mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the skill say to replay with --no-verify and run knip over the finished stack. On v0.1.6: - CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the issue form's version example is 0.1.6-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. - The allowlist is unchanged. Its comments say why ServerEnvironment.ts and server.ts offer and build no triage on a Lazurio Environment (row 15, #147), why ws.ts runs no ChatGPT handoff there and the web starts none through a Lazurio primary (row 18, #145), that useComposerSend.ts counts a prompt toward upstream's star request (pingdotgg#27832) only outside a Lazurio Environment (row 16), and that no update waits on npm since pingdotgg#27847 (row 4). - The contract test pins those seams: the triage guard and its one construction, the star prompt's check and its one call, the handoff route, reconnectProfile and the web's routing, and on Buddy's surface the inline mask over useThreadLifecycle's attentionNow and workNow, every line of it (React Compiler, #135), the items' counts in useThreadLifecycle.tsx and its one caller, the promise ChatView hands Nová karta for a side chat (row 13), and that Buddy's surface offers no side chat (row 25). It also follows the seams upstream moved: no waitForNpm left in the update dialog's logic, the palette's addProjectAction, the sidebar's pickable project groups (pingdotgg#26154), and an embedded side chat (pingdotgg#26901) without thread tabs, terminal drawers or the right panel. Claude's mcp-elicitation requests and the agent scope's kill are covered by rows 30 and 8's own tests. - The runbook's Overlay table describes every row on v0.1.6, the Cílový stack names each row's new commit and the files rows 13, 15, 16 and 18 now change, and the swap step adds mobile-eas-preview-fork.yml to the workflows to disable after the swap. The runbook and the skill say to address a fix written over the finished stack to the row that added the place it changes. On v0.1.7: - CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the issue form's version example is 0.1.7-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. v0.1.7 adds no workflow, so the swap step's list is unchanged. - The allowlist gains toolkits/preview/handlers.ts and its test: since v0.1.7 preview_open takes a dev-server target (pingdotgg#28027), and upstream's handler answered an open with a target with the navigate result alone; row 10 keeps the open answer underneath, so the Environment browser's view stays. The fixed test gate is unchanged. - The contract test follows the seams that moved: the settings writer takes the client's patch for the managed policy (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime notes come from the active session setup, the MCP caller's webOrigin is now hostedAppUrl, the steer guard's waitsOnPendingRequest also holds a delegated task's question (pingdotgg#29909), and the ACP adapter filters T3's options through a flatMap. - For row 30 the allowlist gains apps/web's components/ChatView.logic.ts and its test and components/chat/composerCommandKey.ts, client-runtime's state/composerDispatch.ts and its test, and contracts' orchestrationV2.ts: eight files with the two above. The contract test pins that the web keeps auto input auto while the run is set up; that /compact and /logout wait for no turn; that a running update takes the thread lock on its provider turn's first report or while a follow-up waits, then checks again under the lock; and that each follow-up gets one promotion, so a held one, one already promoted and a refused one stay queued without holding back the next. - Stage 3's checkout command names the release version check's script and test (#165), which the v0.1.6 runbook left out. - The runbook's Overlay table describes every row on v0.1.7, and the Cílový stack names each row's new commit. Main's Cílový stack still named older hashes from row 10 on, so the runbook and the skill now say to take each row's commit from main's log by subject. The runbook also records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices, ManagedPolicy.layerTest()) and that the overlay's settings writes go through updateSettingsWith, so the managed policy vets them. - The runbook records what the independent check of this rebuild found: Codex 0.166.0, T3's managed runtime since v0.1.7, still has default_mode_request_user_input off by default (row 22); mcp-client sessions get hosted thread links on the external origin (row 20); upstream's star prompt now stars through the Environment's account (row 16); the policy lock reads the macOS and Windows sources too (row 18); two upstream policy paths in the update flow do not follow row 4's target and are offered upstream; row 30's refused promotion, /goal and cold-start steer; and row 33's steer page block. The overlay CLI tests build auth on the test managed policy. On v0.1.8: - CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy, whose contact is now security@t3.codes. - The allowlist is unchanged. v0.1.8 adds no workflow, so the swap step's list is unchanged. Upstream's release-desktop.yml can now defer the macOS CLI's notarization with --notary-submission-file; lazurio-cli-archives.yml signs ad hoc, passes no such file and is unchanged. - The contract test follows the seams that moved: the sidebar control takes showSidebar; the composer controls bar's hooks end with the model pick (pingdotgg#31739) and Buddy's controls return after them; an offered prompt suggestion comes before Buddy's placeholder (pingdotgg#28047); and a fresh session after /clear (pingdotgg#30325) never steers, in the web's dispatch mode and in the server's steer and promotion guards. Two new pins keep the Buddy surface's hides of upstream's new entries: "Use in another app" (decision A8) and /clear's fresh session (decision A7). - The runbook's Overlay table describes every row on v0.1.8, the Cílový stack names each row's new commit and files (viewAddressCases.ts in rows 9 and 10), and row 30's text no longer compares waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending user_input. The runbook records this rebuild's conflicts and that a test the rebuild adds belongs in the row's own test file or under apps/*/src/lazurio/, since an upstream test file off the allowlist fails fork CI. On v0.1.9: - CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy. - The allowlist is unchanged. The contract test's seams are unchanged apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name their adaptations in their own messages. - v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in pingdotgg/t3code, and the swap step adds it to the workflows to disable after the swap. The changed ci.yml and four mobile workflows stay disabled. - The runbook's Overlay table describes every row on v0.1.9, the Cílový stack names each row's new commit, and the runbook records this rebuild's conflicts and decisions. Upstream's new screen reader announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's surface, so a screen reader never hears T3's steps there (row 28); the contract test pins that cap in MessagesTimeline.tsx. On v0.1.10: - CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the issue form's version example is 0.1.10-lazurio.1. Upstream moved to Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy; this row adds the fork's section to it. - The allowlist drops branding.ts, ChatView.logic.ts and its test, composerCommandKey.ts and composerDispatch.ts and its test, which the overlay no longer changes: upstream now picks the stage label in branding.logic.ts, and it steers a follow-up sent before the provider turn started (pingdotgg#34581). Row 30 now turns an auto send made then into that deferred steer in Orchestrator.ts and marks it automatic on the queued run, so orchestrationV2.ts stays (#170). It adds sidebar/updateEverythingRun.tsx and its test, where row 4's Retry compares a Lazurio release's whole version, and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry row 4's per-row target; main.test.ts, whose stand-in window carries the address the prompt link capture reads (row 6); and binCli.test.ts, which reads row 21's `t3 thread list --json` with its total. The guard passes both ways on the candidate. - The contract test follows the seams upstream moved: the launcher path now comes from cloud/pinnedRuntime.ts, the build stamps the page title from the stage label (pingdotgg#18442, and no release workflow sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag (sendRuntimeInstructions), the ACP adapter also resets unset options (pingdotgg#35199, held back on Buddy's instance too), provider hydration reads the database config (pingdotgg#34877), a natively resumed thread sends its unsent message (pingdotgg#36526), a failed send gives back the snapshot's draftText (pingdotgg#33124), a linked Environment's sender names it (pingdotgg#34721), an expandable work row's chevron sits between the acting-sender mark and the time (pingdotgg#35549), and the collapsed composer previews the prompt (pingdotgg#22148). Row 30's checks now pin that the one promote-to-steer is upstream's deferred steer, behind the pending-request guard that clears its steerWhenReadyRunId and steerWhenReadyIntent; the conditions under which an auto send in the gap becomes that steer, through resolveMessageDispatchIntent and the adapter's steering or interrupt-and-restart; and the delivery check that lets such a steer in only where the policy steers it then, by the session's capabilities. - v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC; it labels, comments on and closes pull requests, dry-run without PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the swap step disables them right after the swap. The swap push itself starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so the step first cancels that run and then removes any vouch label it gave an open issue. - The Overlay table gains rows 35 to 37 for #214 and #216, and the Cílový stack names their commits on main and their files. Rows 4, 15, 21 and 30 record the fixes from the candidate's independent check (#222); the rest of the table is brought up to v0.1.10 after the release (stage 9). The runbook's "Z přestavby na v0.1.10" records the conflicts, the hand adaptations and those fixes, numbering rows as the table does, and names the replayed main (faae02a, stable 0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216). - Main's #214, #216 and #220 additions to CI, the contract test and the runbook are carried unchanged; #216's narrow-rail pin follows row 36's `hidden` adaptation. A new contract pin holds row 35's hand-placed coordinator change: ThreadNotificationCoordinator.tsx reads hidden threads three times, always as listHiddenThreadKeysAtom, so Buddy's project's threads never sound, toast or notify. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…anel Below 768 px, where T3's left panel is a sheet, the conversation takes the whole width and the Lazurio rail is hidden. Opening the left panel moves the rail into the open panel as its first element, so keyboard and screen readers reach it inside the modal sheet; closing it puts the rail back before #root, where the jump (Mod+Shift+E) still opens visible and ready to type. The wide layout is unchanged. CSS and a short script in index.html; the contract test guards the rule and T3's breakpoint. On v0.1.10 T3 keeps the closed sheet mounted with the hidden attribute, so its thread shortcuts keep working (pingdotgg#23568). The rail goes into the panel only while it is not hidden, and the script watches hidden as well as aria-hidden. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Below 768 px T3's right panel is a sheet of min(88vw, 24rem), with a sliver of the conversation and the rail beside it. With the Lazurio shell it now takes the whole width, like the open left panel; its own toggle or Escape closes it, back to the conversation. CSS only, in index.html's narrow block; the wide layout and T3 outside Lazurio keep upstream's width. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The distribution's files on the new base, upstream T3 Code v0.1.10 (7d32075), last in the stack: CI, the CLI archive, release and upstream watch workflows, the image, the issue form, README, SECURITY.md, the runbook, the overlay spec, the contract test, the release version check and the rebuild's skill. They are main's files, made current for v0.1.10 (#213). Main's base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9 below are kept from the earlier rebuilds. On v0.1.4: - The allowlist gains five files: chat/ThreadServersPanel.tsx, where a click on a thread's server opens it in the Environment browser (row 9); sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts, for the per-server target and the continuation gate of v0.1.4's update dialog (row 4); upstream's installer test install.test.ts, whose fixture needs upstream's repository named (row 4); and cli/environment.ts, whose settings take Buddy's linked-Environments guard (row 25). ServerEnvironment.test.ts keeps the update-check guard (row 4). - The contract test's pins follow the seams that moved: upstream deleted LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column head is pinned in the thread sidebar only; the sidebar reads useDelegatedUnderParent before the managed check; the empty panel and Nová karta carry the workspace focus default; the MCP session issue calls mcpClientScopes directly; an agent command's scope drops the session's web origin so its thread links stay t3-thread:// links; the Buddy composer hook takes only the environment, since v0.1.4's resting composer has no strip of its own; the timeline has no paint-only gate (pingdotgg#25787); the steer guard returns through stopRunForQueuedCommand and also holds a delegated task's completion wake; the Servers panel's click opens the Environment browser; and Buddy's server settings layer turns linked Environments off. - Rows 30, 32 and 33, which main carried as commits after row 31, now sit in their rows; row 28's addenda are back in rows 7, 23 and 25. Upstream renamed the lint rule react-effect-budget to t3code/no-unreasoned-state-sync (pingdotgg#26161). - The skill's inventory groups cover rows 23 to 33. - Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name only fictional people and hosts (Alena, Bob, example-person, vm-0x.example.lazurio.io), since the repository is public. On v0.1.5: - CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy. - The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so lazurio-cli-archives.yml installs patchelf before the build, the way upstream's release-desktop.yml does; the contract test pins the order. - useUpdateEverything.ts leaves the allowlist: row 4 now keeps a server's advertised release out of waitForNpm in updateEverything.logic.ts (pingdotgg#26917), and the contract test pins that seam there. The fixed test gate is unchanged, and every gated path exists at v0.1.5. - The contract test's pairing pins follow the constants that knip made module-private (upstream's pre-commit hook runs knip:check since pingdotgg#26167). - The runbook's Overlay table describes every row on v0.1.5, the Cílový stack names each row's new commit, the swap step names the workflows to disable after the swap from the v0.1.3 base (agent-context-budget.yml, mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the skill say to replay with --no-verify and run knip over the finished stack. On v0.1.6: - CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the issue form's version example is 0.1.6-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. - The allowlist is unchanged. Its comments say why ServerEnvironment.ts and server.ts offer and build no triage on a Lazurio Environment (row 15, #147), why ws.ts runs no ChatGPT handoff there and the web starts none through a Lazurio primary (row 18, #145), that useComposerSend.ts counts a prompt toward upstream's star request (pingdotgg#27832) only outside a Lazurio Environment (row 16), and that no update waits on npm since pingdotgg#27847 (row 4). - The contract test pins those seams: the triage guard and its one construction, the star prompt's check and its one call, the handoff route, reconnectProfile and the web's routing, and on Buddy's surface the inline mask over useThreadLifecycle's attentionNow and workNow, every line of it (React Compiler, #135), the items' counts in useThreadLifecycle.tsx and its one caller, the promise ChatView hands Nová karta for a side chat (row 13), and that Buddy's surface offers no side chat (row 25). It also follows the seams upstream moved: no waitForNpm left in the update dialog's logic, the palette's addProjectAction, the sidebar's pickable project groups (pingdotgg#26154), and an embedded side chat (pingdotgg#26901) without thread tabs, terminal drawers or the right panel. Claude's mcp-elicitation requests and the agent scope's kill are covered by rows 30 and 8's own tests. - The runbook's Overlay table describes every row on v0.1.6, the Cílový stack names each row's new commit and the files rows 13, 15, 16 and 18 now change, and the swap step adds mobile-eas-preview-fork.yml to the workflows to disable after the swap. The runbook and the skill say to address a fix written over the finished stack to the row that added the place it changes. On v0.1.7: - CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the issue form's version example is 0.1.7-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. v0.1.7 adds no workflow, so the swap step's list is unchanged. - The allowlist gains toolkits/preview/handlers.ts and its test: since v0.1.7 preview_open takes a dev-server target (pingdotgg#28027), and upstream's handler answered an open with a target with the navigate result alone; row 10 keeps the open answer underneath, so the Environment browser's view stays. The fixed test gate is unchanged. - The contract test follows the seams that moved: the settings writer takes the client's patch for the managed policy (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime notes come from the active session setup, the MCP caller's webOrigin is now hostedAppUrl, the steer guard's waitsOnPendingRequest also holds a delegated task's question (pingdotgg#29909), and the ACP adapter filters T3's options through a flatMap. - For row 30 the allowlist gains apps/web's components/ChatView.logic.ts and its test and components/chat/composerCommandKey.ts, client-runtime's state/composerDispatch.ts and its test, and contracts' orchestrationV2.ts: eight files with the two above. The contract test pins that the web keeps auto input auto while the run is set up; that /compact and /logout wait for no turn; that a running update takes the thread lock on its provider turn's first report or while a follow-up waits, then checks again under the lock; and that each follow-up gets one promotion, so a held one, one already promoted and a refused one stay queued without holding back the next. - Stage 3's checkout command names the release version check's script and test (#165), which the v0.1.6 runbook left out. - The runbook's Overlay table describes every row on v0.1.7, and the Cílový stack names each row's new commit. Main's Cílový stack still named older hashes from row 10 on, so the runbook and the skill now say to take each row's commit from main's log by subject. The runbook also records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices, ManagedPolicy.layerTest()) and that the overlay's settings writes go through updateSettingsWith, so the managed policy vets them. - The runbook records what the independent check of this rebuild found: Codex 0.166.0, T3's managed runtime since v0.1.7, still has default_mode_request_user_input off by default (row 22); mcp-client sessions get hosted thread links on the external origin (row 20); upstream's star prompt now stars through the Environment's account (row 16); the policy lock reads the macOS and Windows sources too (row 18); two upstream policy paths in the update flow do not follow row 4's target and are offered upstream; row 30's refused promotion, /goal and cold-start steer; and row 33's steer page block. The overlay CLI tests build auth on the test managed policy. On v0.1.8: - CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy, whose contact is now security@t3.codes. - The allowlist is unchanged. v0.1.8 adds no workflow, so the swap step's list is unchanged. Upstream's release-desktop.yml can now defer the macOS CLI's notarization with --notary-submission-file; lazurio-cli-archives.yml signs ad hoc, passes no such file and is unchanged. - The contract test follows the seams that moved: the sidebar control takes showSidebar; the composer controls bar's hooks end with the model pick (pingdotgg#31739) and Buddy's controls return after them; an offered prompt suggestion comes before Buddy's placeholder (pingdotgg#28047); and a fresh session after /clear (pingdotgg#30325) never steers, in the web's dispatch mode and in the server's steer and promotion guards. Two new pins keep the Buddy surface's hides of upstream's new entries: "Use in another app" (decision A8) and /clear's fresh session (decision A7). - The runbook's Overlay table describes every row on v0.1.8, the Cílový stack names each row's new commit and files (viewAddressCases.ts in rows 9 and 10), and row 30's text no longer compares waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending user_input. The runbook records this rebuild's conflicts and that a test the rebuild adds belongs in the row's own test file or under apps/*/src/lazurio/, since an upstream test file off the allowlist fails fork CI. On v0.1.9: - CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy. - The allowlist is unchanged. The contract test's seams are unchanged apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name their adaptations in their own messages. - v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in pingdotgg/t3code, and the swap step adds it to the workflows to disable after the swap. The changed ci.yml and four mobile workflows stay disabled. - The runbook's Overlay table describes every row on v0.1.9, the Cílový stack names each row's new commit, and the runbook records this rebuild's conflicts and decisions. Upstream's new screen reader announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's surface, so a screen reader never hears T3's steps there (row 28); the contract test pins that cap in MessagesTimeline.tsx. On v0.1.10: - CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the issue form's version example is 0.1.10-lazurio.1. Upstream moved to Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy; this row adds the fork's section to it. - The allowlist drops branding.ts, ChatView.logic.ts and its test, composerCommandKey.ts and composerDispatch.ts and its test, which the overlay no longer changes: upstream now picks the stage label in branding.logic.ts, and it steers a follow-up sent before the provider turn started (pingdotgg#34581). Row 30 now turns an auto send made then into that deferred steer in Orchestrator.ts and marks it automatic on the queued run, so orchestrationV2.ts stays (#170). It adds sidebar/updateEverythingRun.tsx and its test, where row 4's Retry compares a Lazurio release's whole version, and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry row 4's per-row target; main.test.ts, whose stand-in window carries the address the prompt link capture reads (row 6); and binCli.test.ts, which reads row 21's `t3 thread list --json` with its total. The guard passes both ways on the candidate. - The contract test follows the seams upstream moved: the launcher path now comes from cloud/pinnedRuntime.ts, the build stamps the page title from the stage label (pingdotgg#18442, and no release workflow sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag (sendRuntimeInstructions), the ACP adapter also resets unset options (pingdotgg#35199, held back on Buddy's instance too), provider hydration reads the database config (pingdotgg#34877), a natively resumed thread sends its unsent message (pingdotgg#36526), a failed send gives back the snapshot's draftText (pingdotgg#33124), a linked Environment's sender names it (pingdotgg#34721), an expandable work row's chevron sits between the acting-sender mark and the time (pingdotgg#35549), and the collapsed composer previews the prompt (pingdotgg#22148). Row 30's checks now pin that the one promote-to-steer is upstream's deferred steer, behind the pending-request guard that clears its steerWhenReadyRunId and steerWhenReadyIntent; the conditions under which an auto send in the gap becomes that steer, through resolveMessageDispatchIntent and the adapter's steering or interrupt-and-restart; and the delivery check that lets such a steer in only where the policy steers it then, by the session's capabilities. - v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC; it labels, comments on and closes pull requests, dry-run without PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the swap step disables them right after the swap. The swap push itself starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so the step first cancels that run and then removes any vouch label it gave an open issue. - The Overlay table gains rows 35 to 37 for #214 and #216, and the Cílový stack names their commits on main and their files. Rows 4, 15, 21 and 30 record the fixes from the candidate's independent check (#222); the rest of the table is brought up to v0.1.10 after the release (stage 9). The runbook's "Z přestavby na v0.1.10" records the conflicts, the hand adaptations and those fixes, numbering rows as the table does, and names the replayed main (faae02a, stable 0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216). - Main's #214, #216 and #220 additions to CI, the contract test and the runbook are carried unchanged; #216's narrow-rail pin follows row 36's `hidden` adaptation. A new contract pin holds row 35's hand-placed coordinator change: ThreadNotificationCoordinator.tsx reads hidden threads three times, always as listHiddenThreadKeysAtom, so Buddy's project's threads never sound, toast or notify. - The review of the candidate at 50a5004 (#222) adds to the runbook: the contract inventory names orchestrationV2.ts with steerWhenReadyIntent only; rows 24 and 30 record the recorded followWakes and the auto steer that a question puts first in the queue; the F50 gate names holders.vectors.test.ts and the vendored Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the new version reads both forms of the launcher, a symlink and since v0.1.10 the script posixLauncherScript writes; and the update channel and its procedure describe the launcher protocol's move from 3 to 4, which an Update from 0.1.9 passes while the 0.1.9 launcher stays until a local update or service install restarts the service. The contract test pins the copied release and the vectors' runner. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…anel Below 768 px, where T3's left panel is a sheet, the conversation takes the whole width and the Lazurio rail is hidden. Opening the left panel moves the rail into the open panel as its first element, so keyboard and screen readers reach it inside the modal sheet; closing it puts the rail back before #root, where the jump (Mod+Shift+E) still opens visible and ready to type. The wide layout is unchanged. CSS and a short script in index.html; the contract test guards the rule and T3's breakpoint. On v0.1.10 T3 keeps the closed sheet mounted with the hidden attribute, so its thread shortcuts keep working (pingdotgg#23568). The rail goes into the panel only while it is not hidden, and the script watches hidden as well as aria-hidden. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Below 768 px T3's right panel is a sheet of min(88vw, 24rem), with a sliver of the conversation and the rail beside it. With the Lazurio shell it now takes the whole width, like the open left panel; its own toggle or Escape closes it, back to the conversation. CSS only, in index.html's narrow block; the wide layout and T3 outside Lazurio keep upstream's width. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The distribution's files on the new base, upstream T3 Code v0.1.10 (7d32075), last in the stack: CI, the CLI archive, release and upstream watch workflows, the image, the issue form, README, SECURITY.md, the runbook, the overlay spec, the contract test, the release version check and the rebuild's skill. They are main's files, made current for v0.1.10 (#213). Main's base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9 below are kept from the earlier rebuilds. On v0.1.4: - The allowlist gains five files: chat/ThreadServersPanel.tsx, where a click on a thread's server opens it in the Environment browser (row 9); sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts, for the per-server target and the continuation gate of v0.1.4's update dialog (row 4); upstream's installer test install.test.ts, whose fixture needs upstream's repository named (row 4); and cli/environment.ts, whose settings take Buddy's linked-Environments guard (row 25). ServerEnvironment.test.ts keeps the update-check guard (row 4). - The contract test's pins follow the seams that moved: upstream deleted LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column head is pinned in the thread sidebar only; the sidebar reads useDelegatedUnderParent before the managed check; the empty panel and Nová karta carry the workspace focus default; the MCP session issue calls mcpClientScopes directly; an agent command's scope drops the session's web origin so its thread links stay t3-thread:// links; the Buddy composer hook takes only the environment, since v0.1.4's resting composer has no strip of its own; the timeline has no paint-only gate (pingdotgg#25787); the steer guard returns through stopRunForQueuedCommand and also holds a delegated task's completion wake; the Servers panel's click opens the Environment browser; and Buddy's server settings layer turns linked Environments off. - Rows 30, 32 and 33, which main carried as commits after row 31, now sit in their rows; row 28's addenda are back in rows 7, 23 and 25. Upstream renamed the lint rule react-effect-budget to t3code/no-unreasoned-state-sync (pingdotgg#26161). - The skill's inventory groups cover rows 23 to 33. - Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name only fictional people and hosts (Alena, Bob, example-person, vm-0x.example.lazurio.io), since the repository is public. On v0.1.5: - CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy. - The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so lazurio-cli-archives.yml installs patchelf before the build, the way upstream's release-desktop.yml does; the contract test pins the order. - useUpdateEverything.ts leaves the allowlist: row 4 now keeps a server's advertised release out of waitForNpm in updateEverything.logic.ts (pingdotgg#26917), and the contract test pins that seam there. The fixed test gate is unchanged, and every gated path exists at v0.1.5. - The contract test's pairing pins follow the constants that knip made module-private (upstream's pre-commit hook runs knip:check since pingdotgg#26167). - The runbook's Overlay table describes every row on v0.1.5, the Cílový stack names each row's new commit, the swap step names the workflows to disable after the swap from the v0.1.3 base (agent-context-budget.yml, mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the skill say to replay with --no-verify and run knip over the finished stack. On v0.1.6: - CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the issue form's version example is 0.1.6-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. - The allowlist is unchanged. Its comments say why ServerEnvironment.ts and server.ts offer and build no triage on a Lazurio Environment (row 15, #147), why ws.ts runs no ChatGPT handoff there and the web starts none through a Lazurio primary (row 18, #145), that useComposerSend.ts counts a prompt toward upstream's star request (pingdotgg#27832) only outside a Lazurio Environment (row 16), and that no update waits on npm since pingdotgg#27847 (row 4). - The contract test pins those seams: the triage guard and its one construction, the star prompt's check and its one call, the handoff route, reconnectProfile and the web's routing, and on Buddy's surface the inline mask over useThreadLifecycle's attentionNow and workNow, every line of it (React Compiler, #135), the items' counts in useThreadLifecycle.tsx and its one caller, the promise ChatView hands Nová karta for a side chat (row 13), and that Buddy's surface offers no side chat (row 25). It also follows the seams upstream moved: no waitForNpm left in the update dialog's logic, the palette's addProjectAction, the sidebar's pickable project groups (pingdotgg#26154), and an embedded side chat (pingdotgg#26901) without thread tabs, terminal drawers or the right panel. Claude's mcp-elicitation requests and the agent scope's kill are covered by rows 30 and 8's own tests. - The runbook's Overlay table describes every row on v0.1.6, the Cílový stack names each row's new commit and the files rows 13, 15, 16 and 18 now change, and the swap step adds mobile-eas-preview-fork.yml to the workflows to disable after the swap. The runbook and the skill say to address a fix written over the finished stack to the row that added the place it changes. On v0.1.7: - CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the issue form's version example is 0.1.7-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. v0.1.7 adds no workflow, so the swap step's list is unchanged. - The allowlist gains toolkits/preview/handlers.ts and its test: since v0.1.7 preview_open takes a dev-server target (pingdotgg#28027), and upstream's handler answered an open with a target with the navigate result alone; row 10 keeps the open answer underneath, so the Environment browser's view stays. The fixed test gate is unchanged. - The contract test follows the seams that moved: the settings writer takes the client's patch for the managed policy (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime notes come from the active session setup, the MCP caller's webOrigin is now hostedAppUrl, the steer guard's waitsOnPendingRequest also holds a delegated task's question (pingdotgg#29909), and the ACP adapter filters T3's options through a flatMap. - For row 30 the allowlist gains apps/web's components/ChatView.logic.ts and its test and components/chat/composerCommandKey.ts, client-runtime's state/composerDispatch.ts and its test, and contracts' orchestrationV2.ts: eight files with the two above. The contract test pins that the web keeps auto input auto while the run is set up; that /compact and /logout wait for no turn; that a running update takes the thread lock on its provider turn's first report or while a follow-up waits, then checks again under the lock; and that each follow-up gets one promotion, so a held one, one already promoted and a refused one stay queued without holding back the next. - Stage 3's checkout command names the release version check's script and test (#165), which the v0.1.6 runbook left out. - The runbook's Overlay table describes every row on v0.1.7, and the Cílový stack names each row's new commit. Main's Cílový stack still named older hashes from row 10 on, so the runbook and the skill now say to take each row's commit from main's log by subject. The runbook also records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices, ManagedPolicy.layerTest()) and that the overlay's settings writes go through updateSettingsWith, so the managed policy vets them. - The runbook records what the independent check of this rebuild found: Codex 0.166.0, T3's managed runtime since v0.1.7, still has default_mode_request_user_input off by default (row 22); mcp-client sessions get hosted thread links on the external origin (row 20); upstream's star prompt now stars through the Environment's account (row 16); the policy lock reads the macOS and Windows sources too (row 18); two upstream policy paths in the update flow do not follow row 4's target and are offered upstream; row 30's refused promotion, /goal and cold-start steer; and row 33's steer page block. The overlay CLI tests build auth on the test managed policy. On v0.1.8: - CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy, whose contact is now security@t3.codes. - The allowlist is unchanged. v0.1.8 adds no workflow, so the swap step's list is unchanged. Upstream's release-desktop.yml can now defer the macOS CLI's notarization with --notary-submission-file; lazurio-cli-archives.yml signs ad hoc, passes no such file and is unchanged. - The contract test follows the seams that moved: the sidebar control takes showSidebar; the composer controls bar's hooks end with the model pick (pingdotgg#31739) and Buddy's controls return after them; an offered prompt suggestion comes before Buddy's placeholder (pingdotgg#28047); and a fresh session after /clear (pingdotgg#30325) never steers, in the web's dispatch mode and in the server's steer and promotion guards. Two new pins keep the Buddy surface's hides of upstream's new entries: "Use in another app" (decision A8) and /clear's fresh session (decision A7). - The runbook's Overlay table describes every row on v0.1.8, the Cílový stack names each row's new commit and files (viewAddressCases.ts in rows 9 and 10), and row 30's text no longer compares waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending user_input. The runbook records this rebuild's conflicts and that a test the rebuild adds belongs in the row's own test file or under apps/*/src/lazurio/, since an upstream test file off the allowlist fails fork CI. On v0.1.9: - CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy. - The allowlist is unchanged. The contract test's seams are unchanged apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name their adaptations in their own messages. - v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in pingdotgg/t3code, and the swap step adds it to the workflows to disable after the swap. The changed ci.yml and four mobile workflows stay disabled. - The runbook's Overlay table describes every row on v0.1.9, the Cílový stack names each row's new commit, and the runbook records this rebuild's conflicts and decisions. Upstream's new screen reader announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's surface, so a screen reader never hears T3's steps there (row 28); the contract test pins that cap in MessagesTimeline.tsx. On v0.1.10: - CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the issue form's version example is 0.1.10-lazurio.1. Upstream moved to Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy; this row adds the fork's section to it. - The allowlist drops branding.ts, ChatView.logic.ts and its test, composerCommandKey.ts and composerDispatch.ts and its test, which the overlay no longer changes: upstream now picks the stage label in branding.logic.ts, and it steers a follow-up sent before the provider turn started (pingdotgg#34581). Row 30 now turns an auto send made then into that deferred steer in Orchestrator.ts and marks it automatic on the queued run, so orchestrationV2.ts stays (#170). It adds sidebar/updateEverythingRun.tsx and its test, where row 4's Retry compares a Lazurio release's whole version, and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry row 4's per-row target; main.test.ts, whose stand-in window carries the address the prompt link capture reads (row 6); and binCli.test.ts, which reads row 21's `t3 thread list --json` with its total. The guard passes both ways on the candidate. - The contract test follows the seams upstream moved: the launcher path now comes from cloud/pinnedRuntime.ts, the build stamps the page title from the stage label (pingdotgg#18442, and no release workflow sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag (sendRuntimeInstructions), the ACP adapter also resets unset options (pingdotgg#35199, held back on Buddy's instance too), provider hydration reads the database config (pingdotgg#34877), a natively resumed thread sends its unsent message (pingdotgg#36526), a failed send gives back the snapshot's draftText (pingdotgg#33124), a linked Environment's sender names it (pingdotgg#34721), an expandable work row's chevron sits between the acting-sender mark and the time (pingdotgg#35549), and the collapsed composer previews the prompt (pingdotgg#22148). Row 30's checks now pin that the one promote-to-steer is upstream's deferred steer, behind the pending-request guard that clears its steerWhenReadyRunId and steerWhenReadyIntent; the conditions under which an auto send in the gap becomes that steer, through resolveMessageDispatchIntent and the adapter's steering or interrupt-and-restart; and the delivery check that lets such a steer in only where the policy steers it then, by the session's capabilities. - v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC; it labels, comments on and closes pull requests, dry-run without PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the swap step disables them right after the swap. The swap push itself starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so the step first cancels that run and then removes any vouch label it gave an open issue. - The Overlay table gains rows 35 to 37 for #214 and #216, and the Cílový stack names their commits on main and their files. Rows 4, 15, 21 and 30 record the fixes from the candidate's independent check (#222); the rest of the table is brought up to v0.1.10 after the release (stage 9). The runbook's "Z přestavby na v0.1.10" records the conflicts, the hand adaptations and those fixes, numbering rows as the table does, and names the replayed main (faae02a, stable 0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216). - Main's #214, #216 and #220 additions to CI, the contract test and the runbook are carried unchanged; #216's narrow-rail pin follows row 36's `hidden` adaptation. A new contract pin holds row 35's hand-placed coordinator change: ThreadNotificationCoordinator.tsx reads hidden threads three times, always as listHiddenThreadKeysAtom, so Buddy's project's threads never sound, toast or notify. - The review of the candidate at 50a5004 (#222) adds to the runbook: the contract inventory names orchestrationV2.ts with steerWhenReadyIntent only; rows 24 and 30 record the recorded followWakes and the auto steer that a question puts first in the queue; the F50 gate names holders.vectors.test.ts and the vendored Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the new version reads both forms of the launcher, a symlink and since v0.1.10 the script posixLauncherScript writes; and the update channel and its procedure describe the launcher protocol's move from 3 to 4, which an Update from 0.1.9 passes while the 0.1.9 launcher stays until a local update or service install restarts the service. The contract test pins the copied release and the vectors' runner. After the next review row 24 records the wait before the send, so a repeat racing the first send cannot record its own; the runbook says so and drops the crash between send and record from the known limits. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…anel Below 768 px, where T3's left panel is a sheet, the conversation takes the whole width and the Lazurio rail is hidden. Opening the left panel moves the rail into the open panel as its first element, so keyboard and screen readers reach it inside the modal sheet; closing it puts the rail back before #root, where the jump (Mod+Shift+E) still opens visible and ready to type. The wide layout is unchanged. CSS and a short script in index.html; the contract test guards the rule and T3's breakpoint. On v0.1.10 T3 keeps the closed sheet mounted with the hidden attribute, so its thread shortcuts keep working (pingdotgg#23568). The rail goes into the panel only while it is not hidden, and the script watches hidden as well as aria-hidden. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Below 768 px T3's right panel is a sheet of min(88vw, 24rem), with a sliver of the conversation and the rail beside it. With the Lazurio shell it now takes the whole width, like the open left panel; its own toggle or Escape closes it, back to the conversation. CSS only, in index.html's narrow block; the wide layout and T3 outside Lazurio keep upstream's width. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The distribution's files on the new base, upstream T3 Code v0.1.10 (7d32075), last in the stack: CI, the CLI archive, release and upstream watch workflows, the image, the issue form, README, SECURITY.md, the runbook, the overlay spec, the contract test, the release version check and the rebuild's skill. They are main's files, made current for v0.1.10 (#213). Main's base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9 below are kept from the earlier rebuilds. On v0.1.4: - The allowlist gains five files: chat/ThreadServersPanel.tsx, where a click on a thread's server opens it in the Environment browser (row 9); sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts, for the per-server target and the continuation gate of v0.1.4's update dialog (row 4); upstream's installer test install.test.ts, whose fixture needs upstream's repository named (row 4); and cli/environment.ts, whose settings take Buddy's linked-Environments guard (row 25). ServerEnvironment.test.ts keeps the update-check guard (row 4). - The contract test's pins follow the seams that moved: upstream deleted LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column head is pinned in the thread sidebar only; the sidebar reads useDelegatedUnderParent before the managed check; the empty panel and Nová karta carry the workspace focus default; the MCP session issue calls mcpClientScopes directly; an agent command's scope drops the session's web origin so its thread links stay t3-thread:// links; the Buddy composer hook takes only the environment, since v0.1.4's resting composer has no strip of its own; the timeline has no paint-only gate (pingdotgg#25787); the steer guard returns through stopRunForQueuedCommand and also holds a delegated task's completion wake; the Servers panel's click opens the Environment browser; and Buddy's server settings layer turns linked Environments off. - Rows 30, 32 and 33, which main carried as commits after row 31, now sit in their rows; row 28's addenda are back in rows 7, 23 and 25. Upstream renamed the lint rule react-effect-budget to t3code/no-unreasoned-state-sync (pingdotgg#26161). - The skill's inventory groups cover rows 23 to 33. - Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name only fictional people and hosts (Alena, Bob, example-person, vm-0x.example.lazurio.io), since the repository is public. On v0.1.5: - CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy. - The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so lazurio-cli-archives.yml installs patchelf before the build, the way upstream's release-desktop.yml does; the contract test pins the order. - useUpdateEverything.ts leaves the allowlist: row 4 now keeps a server's advertised release out of waitForNpm in updateEverything.logic.ts (pingdotgg#26917), and the contract test pins that seam there. The fixed test gate is unchanged, and every gated path exists at v0.1.5. - The contract test's pairing pins follow the constants that knip made module-private (upstream's pre-commit hook runs knip:check since pingdotgg#26167). - The runbook's Overlay table describes every row on v0.1.5, the Cílový stack names each row's new commit, the swap step names the workflows to disable after the swap from the v0.1.3 base (agent-context-budget.yml, mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the skill say to replay with --no-verify and run knip over the finished stack. On v0.1.6: - CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the issue form's version example is 0.1.6-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. - The allowlist is unchanged. Its comments say why ServerEnvironment.ts and server.ts offer and build no triage on a Lazurio Environment (row 15, #147), why ws.ts runs no ChatGPT handoff there and the web starts none through a Lazurio primary (row 18, #145), that useComposerSend.ts counts a prompt toward upstream's star request (pingdotgg#27832) only outside a Lazurio Environment (row 16), and that no update waits on npm since pingdotgg#27847 (row 4). - The contract test pins those seams: the triage guard and its one construction, the star prompt's check and its one call, the handoff route, reconnectProfile and the web's routing, and on Buddy's surface the inline mask over useThreadLifecycle's attentionNow and workNow, every line of it (React Compiler, #135), the items' counts in useThreadLifecycle.tsx and its one caller, the promise ChatView hands Nová karta for a side chat (row 13), and that Buddy's surface offers no side chat (row 25). It also follows the seams upstream moved: no waitForNpm left in the update dialog's logic, the palette's addProjectAction, the sidebar's pickable project groups (pingdotgg#26154), and an embedded side chat (pingdotgg#26901) without thread tabs, terminal drawers or the right panel. Claude's mcp-elicitation requests and the agent scope's kill are covered by rows 30 and 8's own tests. - The runbook's Overlay table describes every row on v0.1.6, the Cílový stack names each row's new commit and the files rows 13, 15, 16 and 18 now change, and the swap step adds mobile-eas-preview-fork.yml to the workflows to disable after the swap. The runbook and the skill say to address a fix written over the finished stack to the row that added the place it changes. On v0.1.7: - CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the issue form's version example is 0.1.7-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. v0.1.7 adds no workflow, so the swap step's list is unchanged. - The allowlist gains toolkits/preview/handlers.ts and its test: since v0.1.7 preview_open takes a dev-server target (pingdotgg#28027), and upstream's handler answered an open with a target with the navigate result alone; row 10 keeps the open answer underneath, so the Environment browser's view stays. The fixed test gate is unchanged. - The contract test follows the seams that moved: the settings writer takes the client's patch for the managed policy (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime notes come from the active session setup, the MCP caller's webOrigin is now hostedAppUrl, the steer guard's waitsOnPendingRequest also holds a delegated task's question (pingdotgg#29909), and the ACP adapter filters T3's options through a flatMap. - For row 30 the allowlist gains apps/web's components/ChatView.logic.ts and its test and components/chat/composerCommandKey.ts, client-runtime's state/composerDispatch.ts and its test, and contracts' orchestrationV2.ts: eight files with the two above. The contract test pins that the web keeps auto input auto while the run is set up; that /compact and /logout wait for no turn; that a running update takes the thread lock on its provider turn's first report or while a follow-up waits, then checks again under the lock; and that each follow-up gets one promotion, so a held one, one already promoted and a refused one stay queued without holding back the next. - Stage 3's checkout command names the release version check's script and test (#165), which the v0.1.6 runbook left out. - The runbook's Overlay table describes every row on v0.1.7, and the Cílový stack names each row's new commit. Main's Cílový stack still named older hashes from row 10 on, so the runbook and the skill now say to take each row's commit from main's log by subject. The runbook also records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices, ManagedPolicy.layerTest()) and that the overlay's settings writes go through updateSettingsWith, so the managed policy vets them. - The runbook records what the independent check of this rebuild found: Codex 0.166.0, T3's managed runtime since v0.1.7, still has default_mode_request_user_input off by default (row 22); mcp-client sessions get hosted thread links on the external origin (row 20); upstream's star prompt now stars through the Environment's account (row 16); the policy lock reads the macOS and Windows sources too (row 18); two upstream policy paths in the update flow do not follow row 4's target and are offered upstream; row 30's refused promotion, /goal and cold-start steer; and row 33's steer page block. The overlay CLI tests build auth on the test managed policy. On v0.1.8: - CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy, whose contact is now security@t3.codes. - The allowlist is unchanged. v0.1.8 adds no workflow, so the swap step's list is unchanged. Upstream's release-desktop.yml can now defer the macOS CLI's notarization with --notary-submission-file; lazurio-cli-archives.yml signs ad hoc, passes no such file and is unchanged. - The contract test follows the seams that moved: the sidebar control takes showSidebar; the composer controls bar's hooks end with the model pick (pingdotgg#31739) and Buddy's controls return after them; an offered prompt suggestion comes before Buddy's placeholder (pingdotgg#28047); and a fresh session after /clear (pingdotgg#30325) never steers, in the web's dispatch mode and in the server's steer and promotion guards. Two new pins keep the Buddy surface's hides of upstream's new entries: "Use in another app" (decision A8) and /clear's fresh session (decision A7). - The runbook's Overlay table describes every row on v0.1.8, the Cílový stack names each row's new commit and files (viewAddressCases.ts in rows 9 and 10), and row 30's text no longer compares waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending user_input. The runbook records this rebuild's conflicts and that a test the rebuild adds belongs in the row's own test file or under apps/*/src/lazurio/, since an upstream test file off the allowlist fails fork CI. On v0.1.9: - CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy. - The allowlist is unchanged. The contract test's seams are unchanged apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name their adaptations in their own messages. - v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in pingdotgg/t3code, and the swap step adds it to the workflows to disable after the swap. The changed ci.yml and four mobile workflows stay disabled. - The runbook's Overlay table describes every row on v0.1.9, the Cílový stack names each row's new commit, and the runbook records this rebuild's conflicts and decisions. Upstream's new screen reader announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's surface, so a screen reader never hears T3's steps there (row 28); the contract test pins that cap in MessagesTimeline.tsx. On v0.1.10: - CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the issue form's version example is 0.1.10-lazurio.1. Upstream moved to Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy; this row adds the fork's section to it. - The allowlist drops branding.ts, ChatView.logic.ts and its test, composerCommandKey.ts and composerDispatch.ts and its test, which the overlay no longer changes: upstream now picks the stage label in branding.logic.ts, and it steers a follow-up sent before the provider turn started (pingdotgg#34581). Row 30 now turns an auto send made then into that deferred steer in Orchestrator.ts and marks it automatic on the queued run, so orchestrationV2.ts stays (#170). It adds sidebar/updateEverythingRun.tsx and its test, where row 4's Retry compares a Lazurio release's whole version, and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry row 4's per-row target; main.test.ts, whose stand-in window carries the address the prompt link capture reads (row 6); and binCli.test.ts, which reads row 21's `t3 thread list --json` with its total. The guard passes both ways on the candidate. - The contract test follows the seams upstream moved: the launcher path now comes from cloud/pinnedRuntime.ts, the build stamps the page title from the stage label (pingdotgg#18442, and no release workflow sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag (sendRuntimeInstructions), the ACP adapter also resets unset options (pingdotgg#35199, held back on Buddy's instance too), provider hydration reads the database config (pingdotgg#34877), a natively resumed thread sends its unsent message (pingdotgg#36526), a failed send gives back the snapshot's draftText (pingdotgg#33124), a linked Environment's sender names it (pingdotgg#34721), an expandable work row's chevron sits between the acting-sender mark and the time (pingdotgg#35549), and the collapsed composer previews the prompt (pingdotgg#22148). Row 30's checks now pin that the one promote-to-steer is upstream's deferred steer, behind the pending-request guard that clears its steerWhenReadyRunId and steerWhenReadyIntent; the conditions under which an auto send in the gap becomes that steer, through resolveMessageDispatchIntent and the adapter's steering or interrupt-and-restart; and the delivery check that lets such a steer in only where the policy steers it then, by the session's capabilities. - v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC; it labels, comments on and closes pull requests, dry-run without PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the swap step disables them right after the swap. The swap push itself starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so the step first cancels that run and then removes any vouch label it gave an open issue. - The Overlay table gains rows 35 to 37 for #214 and #216, and the Cílový stack names their commits on main and their files. Rows 4, 15, 21 and 30 record the fixes from the candidate's independent check (#222); the rest of the table is brought up to v0.1.10 after the release (stage 9). The runbook's "Z přestavby na v0.1.10" records the conflicts, the hand adaptations and those fixes, numbering rows as the table does, and names the replayed main (faae02a, stable 0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216). - Main's #214, #216 and #220 additions to CI, the contract test and the runbook are carried unchanged; #216's narrow-rail pin follows row 36's `hidden` adaptation. A new contract pin holds row 35's hand-placed coordinator change: ThreadNotificationCoordinator.tsx reads hidden threads three times, always as listHiddenThreadKeysAtom, so Buddy's project's threads never sound, toast or notify. - The review of the candidate at 50a5004 (#222) adds to the runbook: the contract inventory names orchestrationV2.ts with steerWhenReadyIntent only; rows 24 and 30 record the recorded followWakes and the auto steer that a question puts first in the queue; the F50 gate names holders.vectors.test.ts and the vendored Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the new version reads both forms of the launcher, a symlink and since v0.1.10 the script posixLauncherScript writes; and the update channel and its procedure describe the launcher protocol's move from 3 to 4, which an Update from 0.1.9 passes while the 0.1.9 launcher stays until a local update or service install restarts the service. The contract test pins the copied release and the vectors' runner. After the next review row 24 records the wait before the send, so a repeat racing the first send cannot record its own; the runbook says so and drops the crash between send and record from the known limits. After the review after that, T3 records the wait only until it accepts the key's command and each send reads the last record after it sent, so a send that fails between record and dispatch leaves no wait a retry follows; the contract test pins the record before the send, the read after it and the receipt check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…anel Below 768 px, where T3's left panel is a sheet, the conversation takes the whole width and the Lazurio rail is hidden. Opening the left panel moves the rail into the open panel as its first element, so keyboard and screen readers reach it inside the modal sheet; closing it puts the rail back before #root, where the jump (Mod+Shift+E) still opens visible and ready to type. The wide layout is unchanged. CSS and a short script in index.html; the contract test guards the rule and T3's breakpoint. On v0.1.10 T3 keeps the closed sheet mounted with the hidden attribute, so its thread shortcuts keep working (pingdotgg#23568). The rail goes into the panel only while it is not hidden, and the script watches hidden as well as aria-hidden. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Below 768 px T3's right panel is a sheet of min(88vw, 24rem), with a sliver of the conversation and the rail beside it. With the Lazurio shell it now takes the whole width, like the open left panel; its own toggle or Escape closes it, back to the conversation. CSS only, in index.html's narrow block; the wide layout and T3 outside Lazurio keep upstream's width. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The distribution's files on the new base, upstream T3 Code v0.1.10 (7d32075), last in the stack: CI, the CLI archive, release and upstream watch workflows, the image, the issue form, README, SECURITY.md, the runbook, the overlay spec, the contract test, the release version check and the rebuild's skill. They are main's files, made current for v0.1.10 (#213). Main's base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9 below are kept from the earlier rebuilds. On v0.1.4: - The allowlist gains five files: chat/ThreadServersPanel.tsx, where a click on a thread's server opens it in the Environment browser (row 9); sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts, for the per-server target and the continuation gate of v0.1.4's update dialog (row 4); upstream's installer test install.test.ts, whose fixture needs upstream's repository named (row 4); and cli/environment.ts, whose settings take Buddy's linked-Environments guard (row 25). ServerEnvironment.test.ts keeps the update-check guard (row 4). - The contract test's pins follow the seams that moved: upstream deleted LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column head is pinned in the thread sidebar only; the sidebar reads useDelegatedUnderParent before the managed check; the empty panel and Nová karta carry the workspace focus default; the MCP session issue calls mcpClientScopes directly; an agent command's scope drops the session's web origin so its thread links stay t3-thread:// links; the Buddy composer hook takes only the environment, since v0.1.4's resting composer has no strip of its own; the timeline has no paint-only gate (pingdotgg#25787); the steer guard returns through stopRunForQueuedCommand and also holds a delegated task's completion wake; the Servers panel's click opens the Environment browser; and Buddy's server settings layer turns linked Environments off. - Rows 30, 32 and 33, which main carried as commits after row 31, now sit in their rows; row 28's addenda are back in rows 7, 23 and 25. Upstream renamed the lint rule react-effect-budget to t3code/no-unreasoned-state-sync (pingdotgg#26161). - The skill's inventory groups cover rows 23 to 33. - Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name only fictional people and hosts (Alena, Bob, example-person, vm-0x.example.lazurio.io), since the repository is public. On v0.1.5: - CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy. - The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so lazurio-cli-archives.yml installs patchelf before the build, the way upstream's release-desktop.yml does; the contract test pins the order. - useUpdateEverything.ts leaves the allowlist: row 4 now keeps a server's advertised release out of waitForNpm in updateEverything.logic.ts (pingdotgg#26917), and the contract test pins that seam there. The fixed test gate is unchanged, and every gated path exists at v0.1.5. - The contract test's pairing pins follow the constants that knip made module-private (upstream's pre-commit hook runs knip:check since pingdotgg#26167). - The runbook's Overlay table describes every row on v0.1.5, the Cílový stack names each row's new commit, the swap step names the workflows to disable after the swap from the v0.1.3 base (agent-context-budget.yml, mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the skill say to replay with --no-verify and run knip over the finished stack. On v0.1.6: - CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the issue form's version example is 0.1.6-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. - The allowlist is unchanged. Its comments say why ServerEnvironment.ts and server.ts offer and build no triage on a Lazurio Environment (row 15, #147), why ws.ts runs no ChatGPT handoff there and the web starts none through a Lazurio primary (row 18, #145), that useComposerSend.ts counts a prompt toward upstream's star request (pingdotgg#27832) only outside a Lazurio Environment (row 16), and that no update waits on npm since pingdotgg#27847 (row 4). - The contract test pins those seams: the triage guard and its one construction, the star prompt's check and its one call, the handoff route, reconnectProfile and the web's routing, and on Buddy's surface the inline mask over useThreadLifecycle's attentionNow and workNow, every line of it (React Compiler, #135), the items' counts in useThreadLifecycle.tsx and its one caller, the promise ChatView hands Nová karta for a side chat (row 13), and that Buddy's surface offers no side chat (row 25). It also follows the seams upstream moved: no waitForNpm left in the update dialog's logic, the palette's addProjectAction, the sidebar's pickable project groups (pingdotgg#26154), and an embedded side chat (pingdotgg#26901) without thread tabs, terminal drawers or the right panel. Claude's mcp-elicitation requests and the agent scope's kill are covered by rows 30 and 8's own tests. - The runbook's Overlay table describes every row on v0.1.6, the Cílový stack names each row's new commit and the files rows 13, 15, 16 and 18 now change, and the swap step adds mobile-eas-preview-fork.yml to the workflows to disable after the swap. The runbook and the skill say to address a fix written over the finished stack to the row that added the place it changes. On v0.1.7: - CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the issue form's version example is 0.1.7-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. v0.1.7 adds no workflow, so the swap step's list is unchanged. - The allowlist gains toolkits/preview/handlers.ts and its test: since v0.1.7 preview_open takes a dev-server target (pingdotgg#28027), and upstream's handler answered an open with a target with the navigate result alone; row 10 keeps the open answer underneath, so the Environment browser's view stays. The fixed test gate is unchanged. - The contract test follows the seams that moved: the settings writer takes the client's patch for the managed policy (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime notes come from the active session setup, the MCP caller's webOrigin is now hostedAppUrl, the steer guard's waitsOnPendingRequest also holds a delegated task's question (pingdotgg#29909), and the ACP adapter filters T3's options through a flatMap. - For row 30 the allowlist gains apps/web's components/ChatView.logic.ts and its test and components/chat/composerCommandKey.ts, client-runtime's state/composerDispatch.ts and its test, and contracts' orchestrationV2.ts: eight files with the two above. The contract test pins that the web keeps auto input auto while the run is set up; that /compact and /logout wait for no turn; that a running update takes the thread lock on its provider turn's first report or while a follow-up waits, then checks again under the lock; and that each follow-up gets one promotion, so a held one, one already promoted and a refused one stay queued without holding back the next. - Stage 3's checkout command names the release version check's script and test (#165), which the v0.1.6 runbook left out. - The runbook's Overlay table describes every row on v0.1.7, and the Cílový stack names each row's new commit. Main's Cílový stack still named older hashes from row 10 on, so the runbook and the skill now say to take each row's commit from main's log by subject. The runbook also records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices, ManagedPolicy.layerTest()) and that the overlay's settings writes go through updateSettingsWith, so the managed policy vets them. - The runbook records what the independent check of this rebuild found: Codex 0.166.0, T3's managed runtime since v0.1.7, still has default_mode_request_user_input off by default (row 22); mcp-client sessions get hosted thread links on the external origin (row 20); upstream's star prompt now stars through the Environment's account (row 16); the policy lock reads the macOS and Windows sources too (row 18); two upstream policy paths in the update flow do not follow row 4's target and are offered upstream; row 30's refused promotion, /goal and cold-start steer; and row 33's steer page block. The overlay CLI tests build auth on the test managed policy. On v0.1.8: - CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy, whose contact is now security@t3.codes. - The allowlist is unchanged. v0.1.8 adds no workflow, so the swap step's list is unchanged. Upstream's release-desktop.yml can now defer the macOS CLI's notarization with --notary-submission-file; lazurio-cli-archives.yml signs ad hoc, passes no such file and is unchanged. - The contract test follows the seams that moved: the sidebar control takes showSidebar; the composer controls bar's hooks end with the model pick (pingdotgg#31739) and Buddy's controls return after them; an offered prompt suggestion comes before Buddy's placeholder (pingdotgg#28047); and a fresh session after /clear (pingdotgg#30325) never steers, in the web's dispatch mode and in the server's steer and promotion guards. Two new pins keep the Buddy surface's hides of upstream's new entries: "Use in another app" (decision A8) and /clear's fresh session (decision A7). - The runbook's Overlay table describes every row on v0.1.8, the Cílový stack names each row's new commit and files (viewAddressCases.ts in rows 9 and 10), and row 30's text no longer compares waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending user_input. The runbook records this rebuild's conflicts and that a test the rebuild adds belongs in the row's own test file or under apps/*/src/lazurio/, since an upstream test file off the allowlist fails fork CI. On v0.1.9: - CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy. - The allowlist is unchanged. The contract test's seams are unchanged apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name their adaptations in their own messages. - v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in pingdotgg/t3code, and the swap step adds it to the workflows to disable after the swap. The changed ci.yml and four mobile workflows stay disabled. - The runbook's Overlay table describes every row on v0.1.9, the Cílový stack names each row's new commit, and the runbook records this rebuild's conflicts and decisions. Upstream's new screen reader announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's surface, so a screen reader never hears T3's steps there (row 28); the contract test pins that cap in MessagesTimeline.tsx. On v0.1.10: - CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the issue form's version example is 0.1.10-lazurio.1. Upstream moved to Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy; this row adds the fork's section to it. - The allowlist drops branding.ts, ChatView.logic.ts and its test, composerCommandKey.ts and composerDispatch.ts and its test, which the overlay no longer changes: upstream now picks the stage label in branding.logic.ts, and it steers a follow-up sent before the provider turn started (pingdotgg#34581). Row 30 now turns an auto send made then into that deferred steer in Orchestrator.ts and marks it automatic on the queued run, so orchestrationV2.ts stays (#170). It adds sidebar/updateEverythingRun.tsx and its test, where row 4's Retry compares a Lazurio release's whole version, and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry row 4's per-row target; main.test.ts, whose stand-in window carries the address the prompt link capture reads (row 6); and binCli.test.ts, which reads row 21's `t3 thread list --json` with its total. The guard passes both ways on the candidate. - The contract test follows the seams upstream moved: the launcher path now comes from cloud/pinnedRuntime.ts, the build stamps the page title from the stage label (pingdotgg#18442, and no release workflow sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag (sendRuntimeInstructions), the ACP adapter also resets unset options (pingdotgg#35199, held back on Buddy's instance too), provider hydration reads the database config (pingdotgg#34877), a natively resumed thread sends its unsent message (pingdotgg#36526), a failed send gives back the snapshot's draftText (pingdotgg#33124), a linked Environment's sender names it (pingdotgg#34721), an expandable work row's chevron sits between the acting-sender mark and the time (pingdotgg#35549), and the collapsed composer previews the prompt (pingdotgg#22148). Row 30's checks now pin that the one promote-to-steer is upstream's deferred steer, behind the pending-request guard that clears its steerWhenReadyRunId and steerWhenReadyIntent; the conditions under which an auto send in the gap becomes that steer, through resolveMessageDispatchIntent and the adapter's steering or interrupt-and-restart; and the delivery check that lets such a steer in only where the policy steers it then, by the session's capabilities. - v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC; it labels, comments on and closes pull requests, dry-run without PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the swap step disables them right after the swap. The swap push itself starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so the step first cancels that run and then removes any vouch label it gave an open issue. - The Overlay table gains rows 35 to 37 for #214 and #216, and the Cílový stack names their commits on main and their files. Rows 4, 15, 21 and 30 record the fixes from the candidate's independent check (#222); the rest of the table is brought up to v0.1.10 after the release (stage 9). The runbook's "Z přestavby na v0.1.10" records the conflicts, the hand adaptations and those fixes, numbering rows as the table does, and names the replayed main (faae02a, stable 0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216). - Main's #214, #216 and #220 additions to CI, the contract test and the runbook are carried unchanged; #216's narrow-rail pin follows row 36's `hidden` adaptation. A new contract pin holds row 35's hand-placed coordinator change: ThreadNotificationCoordinator.tsx reads hidden threads three times, always as listHiddenThreadKeysAtom, so Buddy's project's threads never sound, toast or notify. - The review of the candidate at 50a5004 (#222) adds to the runbook: the contract inventory names orchestrationV2.ts with steerWhenReadyIntent only; rows 24 and 30 record the recorded followWakes and the auto steer that a question puts first in the queue; the F50 gate names holders.vectors.test.ts and the vendored Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the new version reads both forms of the launcher, a symlink and since v0.1.10 the script posixLauncherScript writes; and the update channel and its procedure describe the launcher protocol's move from 3 to 4, which an Update from 0.1.9 passes while the 0.1.9 launcher stays until a local update or service install restarts the service. The contract test pins the copied release and the vectors' runner. After the next review row 24 records the wait before the send, so a repeat racing the first send cannot record its own; the runbook says so and drops the crash between send and record from the known limits. After the review after that, T3 records the wait only until it accepts the key's command and each send reads the last record after it sent, so a send that fails between record and dispatch leaves no wait a retry follows; the contract test pins the record before the send, the read after it and the receipt check. After the review on c5cf16b, each keyed send claims its key before it sends and only the claim's holder sends, so the wait T3 keeps is the accepted send's; the runbook describes the claim, the send_in_progress refusal, CLAIM_TTL_MS and the limits, and the contract test pins the claim, the refusal, the release, the expiry and the receipt gate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…anel Below 768 px, where T3's left panel is a sheet, the conversation takes the whole width and the Lazurio rail is hidden. Opening the left panel moves the rail into the open panel as its first element, so keyboard and screen readers reach it inside the modal sheet; closing it puts the rail back before #root, where the jump (Mod+Shift+E) still opens visible and ready to type. The wide layout is unchanged. CSS and a short script in index.html; the contract test guards the rule and T3's breakpoint. On v0.1.10 T3 keeps the closed sheet mounted with the hidden attribute, so its thread shortcuts keep working (pingdotgg#23568). The rail goes into the panel only while it is not hidden, and the script watches hidden as well as aria-hidden. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Below 768 px T3's right panel is a sheet of min(88vw, 24rem), with a sliver of the conversation and the rail beside it. With the Lazurio shell it now takes the whole width, like the open left panel; its own toggle or Escape closes it, back to the conversation. CSS only, in index.html's narrow block; the wide layout and T3 outside Lazurio keep upstream's width. #216. Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · bot c59bfd74-62a6-4eaa-88dd-5e19f1b3032e Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The distribution's files on the new base, upstream T3 Code v0.1.10 (7d32075), last in the stack: CI, the CLI archive, release and upstream watch workflows, the image, the issue form, README, SECURITY.md, the runbook, the overlay spec, the contract test, the release version check and the rebuild's skill. They are main's files, made current for v0.1.10 (#213). Main's base is v0.1.9 (#185); the notes for v0.1.4 to v0.1.9 below are kept from the earlier rebuilds. On v0.1.4: - The allowlist gains five files: chat/ThreadServersPanel.tsx, where a click on a thread's server opens it in the Environment browser (row 9); sidebar/UpdateEverythingDialog.tsx and updateEverything.logic.test.ts, for the per-server target and the continuation gate of v0.1.4's update dialog (row 4); upstream's installer test install.test.ts, whose fixture needs upstream's repository named (row 4); and cli/environment.ts, whose settings take Buddy's linked-Environments guard (row 25). ServerEnvironment.test.ts keeps the update-check guard (row 4). - The contract test's pins follow the seams that moved: upstream deleted LegacySidebar.tsx (pingdotgg#21039), so the shell slot's column head is pinned in the thread sidebar only; the sidebar reads useDelegatedUnderParent before the managed check; the empty panel and Nová karta carry the workspace focus default; the MCP session issue calls mcpClientScopes directly; an agent command's scope drops the session's web origin so its thread links stay t3-thread:// links; the Buddy composer hook takes only the environment, since v0.1.4's resting composer has no strip of its own; the timeline has no paint-only gate (pingdotgg#25787); the steer guard returns through stopRunForQueuedCommand and also holds a delegated task's completion wake; the Servers panel's click opens the Environment browser; and Buddy's server settings layer turns linked Environments off. - Rows 30, 32 and 33, which main carried as commits after row 31, now sit in their rows; row 28's addenda are back in rows 7, 23 and 25. Upstream renamed the lint rule react-effect-budget to t3code/no-unreasoned-state-sync (pingdotgg#26161). - The skill's inventory groups cover rows 23 to 33. - Tests, fixtures and docs of rows 9, 10, 21, 23, 25, 26 and 27 name only fictional people and hosts (Alena, Bob, example-person, vm-0x.example.lazurio.io), since the repository is public. On v0.1.5: - CI and the contract test pin v0.1.5 and build 0.1.5-lazurio.0; the issue form's version example is 0.1.5-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy. - The Linux CLI archive now ships lib/libatomic.so.1 and patchelf sets t3's RUNPATH to it (pingdotgg#26912, pingdotgg#26932), so lazurio-cli-archives.yml installs patchelf before the build, the way upstream's release-desktop.yml does; the contract test pins the order. - useUpdateEverything.ts leaves the allowlist: row 4 now keeps a server's advertised release out of waitForNpm in updateEverything.logic.ts (pingdotgg#26917), and the contract test pins that seam there. The fixed test gate is unchanged, and every gated path exists at v0.1.5. - The contract test's pairing pins follow the constants that knip made module-private (upstream's pre-commit hook runs knip:check since pingdotgg#26167). - The runbook's Overlay table describes every row on v0.1.5, the Cílový stack names each row's new commit, the swap step names the workflows to disable after the swap from the v0.1.3 base (agent-context-budget.yml, mobile-fingerprint-label.yml; v0.1.5 adds none), and stage 3 and the skill say to replay with --no-verify and run knip over the finished stack. On v0.1.6: - CI and the contract test pin v0.1.6 and build 0.1.6-lazurio.0; the issue form's version example is 0.1.6-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. - The allowlist is unchanged. Its comments say why ServerEnvironment.ts and server.ts offer and build no triage on a Lazurio Environment (row 15, #147), why ws.ts runs no ChatGPT handoff there and the web starts none through a Lazurio primary (row 18, #145), that useComposerSend.ts counts a prompt toward upstream's star request (pingdotgg#27832) only outside a Lazurio Environment (row 16), and that no update waits on npm since pingdotgg#27847 (row 4). - The contract test pins those seams: the triage guard and its one construction, the star prompt's check and its one call, the handoff route, reconnectProfile and the web's routing, and on Buddy's surface the inline mask over useThreadLifecycle's attentionNow and workNow, every line of it (React Compiler, #135), the items' counts in useThreadLifecycle.tsx and its one caller, the promise ChatView hands Nová karta for a side chat (row 13), and that Buddy's surface offers no side chat (row 25). It also follows the seams upstream moved: no waitForNpm left in the update dialog's logic, the palette's addProjectAction, the sidebar's pickable project groups (pingdotgg#26154), and an embedded side chat (pingdotgg#26901) without thread tabs, terminal drawers or the right panel. Claude's mcp-elicitation requests and the agent scope's kill are covered by rows 30 and 8's own tests. - The runbook's Overlay table describes every row on v0.1.6, the Cílový stack names each row's new commit and the files rows 13, 15, 16 and 18 now change, and the swap step adds mobile-eas-preview-fork.yml to the workflows to disable after the swap. The runbook and the skill say to address a fix written over the finished stack to the row that added the place it changes. On v0.1.7: - CI and the contract test pin v0.1.7 and build 0.1.7-lazurio.0; the issue form's version example is 0.1.7-lazurio.1. The toolchain pins hold, and SECURITY.md's upstream section equals the new tag's policy. v0.1.7 adds no workflow, so the swap step's list is unchanged. - The allowlist gains toolkits/preview/handlers.ts and its test: since v0.1.7 preview_open takes a dev-server target (pingdotgg#28027), and upstream's handler answered an open with a target with the navigate result alone; row 10 keeps the open answer underneath, so the Environment browser's view stays. The fixed test gate is unchanged. - The contract test follows the seams that moved: the settings writer takes the client's patch for the managed policy (updateAndPersistSettings, pingdotgg#27197), Hermes's runtime notes come from the active session setup, the MCP caller's webOrigin is now hostedAppUrl, the steer guard's waitsOnPendingRequest also holds a delegated task's question (pingdotgg#29909), and the ACP adapter filters T3's options through a flatMap. - For row 30 the allowlist gains apps/web's components/ChatView.logic.ts and its test and components/chat/composerCommandKey.ts, client-runtime's state/composerDispatch.ts and its test, and contracts' orchestrationV2.ts: eight files with the two above. The contract test pins that the web keeps auto input auto while the run is set up; that /compact and /logout wait for no turn; that a running update takes the thread lock on its provider turn's first report or while a follow-up waits, then checks again under the lock; and that each follow-up gets one promotion, so a held one, one already promoted and a refused one stay queued without holding back the next. - Stage 3's checkout command names the release version check's script and test (#165), which the v0.1.6 runbook left out. - The runbook's Overlay table describes every row on v0.1.7, and the Cílový stack names each row's new commit. Main's Cílový stack still named older hashes from row 10 on, so the runbook and the skill now say to take each row's commit from main's log by subject. The runbook also records the Effect 4.1.2 test recipe (NodeCrypto beside NodeServices, ManagedPolicy.layerTest()) and that the overlay's settings writes go through updateSettingsWith, so the managed policy vets them. - The runbook records what the independent check of this rebuild found: Codex 0.166.0, T3's managed runtime since v0.1.7, still has default_mode_request_user_input off by default (row 22); mcp-client sessions get hosted thread links on the external origin (row 20); upstream's star prompt now stars through the Environment's account (row 16); the policy lock reads the macOS and Windows sources too (row 18); two upstream policy paths in the update flow do not follow row 4's target and are offered upstream; row 30's refused promotion, /goal and cold-start steer; and row 33's steer page block. The overlay CLI tests build auth on the test managed policy. On v0.1.8: - CI and the contract test pin v0.1.8 and build 0.1.8-lazurio.0; the issue form's version example is 0.1.8-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. SECURITY.md's upstream section equals the new tag's policy, whose contact is now security@t3.codes. - The allowlist is unchanged. v0.1.8 adds no workflow, so the swap step's list is unchanged. Upstream's release-desktop.yml can now defer the macOS CLI's notarization with --notary-submission-file; lazurio-cli-archives.yml signs ad hoc, passes no such file and is unchanged. - The contract test follows the seams that moved: the sidebar control takes showSidebar; the composer controls bar's hooks end with the model pick (pingdotgg#31739) and Buddy's controls return after them; an offered prompt suggestion comes before Buddy's placeholder (pingdotgg#28047); and a fresh session after /clear (pingdotgg#30325) never steers, in the web's dispatch mode and in the server's steer and promotion guards. Two new pins keep the Buddy surface's hides of upstream's new entries: "Use in another app" (decision A8) and /clear's fresh session (decision A7). - The runbook's Overlay table describes every row on v0.1.8, the Cílový stack names each row's new commit and files (viewAddressCases.ts in rows 9 and 10), and row 30's text no longer compares waitsOnPendingRequest with snooze, which since v0.1.8 ignores a pending user_input. The runbook records this rebuild's conflicts and that a test the rebuild adds belongs in the row's own test file or under apps/*/src/lazurio/, since an upstream test file off the allowlist fails fork CI. On v0.1.9: - CI and the contract test pin v0.1.9 and build 0.1.9-lazurio.0; the issue form's version example is 0.1.9-lazurio.1. Node 26.12.1 and pnpm 12.14.0 are unchanged, so the toolchain pins hold. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy. - The allowlist is unchanged. The contract test's seams are unchanged apart from one new pin, and the tag and SHA pins move. The stack replays the approved v0.1.8 candidate (#187) on v0.1.9, and rows 4, 9, 15, 28 and 30 name their adaptations in their own messages. - v0.1.9 adds mobile-dev-client.yml (push to main, pull_request on its own file and scripts/mobile-native-client.ts, workflow_dispatch); both its jobs run only in pingdotgg/t3code, and the swap step adds it to the workflows to disable after the swap. The changed ci.yml and four mobile workflows stay disabled. - The runbook's Overlay table describes every row on v0.1.9, the Cílový stack names each row's new commit, and the runbook records this rebuild's conflicts and decisions. Upstream's new screen reader announcements (pingdotgg#33900) are capped at Buddy's messages on Buddy's surface, so a screen reader never hears T3's steps there (row 28); the contract test pins that cap in MessagesTimeline.tsx. On v0.1.10: - CI and the contract test pin v0.1.10 and build 0.1.10-lazurio.0; the issue form's version example is 0.1.10-lazurio.1. Upstream moved to Node 26.13.1 (pnpm 12.14.0 is unchanged), so CI, the release and the image pin Node 26.13.1 and node:26.13.1-bookworm by its index digest. Upstream left SECURITY.md unchanged, so its upstream section still equals the tag's policy; this row adds the fork's section to it. - The allowlist drops branding.ts, ChatView.logic.ts and its test, composerCommandKey.ts and composerDispatch.ts and its test, which the overlay no longer changes: upstream now picks the stage label in branding.logic.ts, and it steers a follow-up sent before the provider turn started (pingdotgg#34581). Row 30 now turns an auto send made then into that deferred steer in Orchestrator.ts and marks it automatic on the queued run, so orchestrationV2.ts stays (#170). It adds sidebar/updateEverythingRun.tsx and its test, where row 4's Retry compares a Lazurio release's whole version, and three new upstream tests: SidebarUpdatePill.browser.test.tsx, whose rows carry row 4's per-row target; main.test.ts, whose stand-in window carries the address the prompt link capture reads (row 6); and binCli.test.ts, which reads row 21's `t3 thread list --json` with its total. The guard passes both ways on the candidate. - The contract test follows the seams upstream moved: the launcher path now comes from cloud/pinnedRuntime.ts, the build stamps the page title from the stage label (pingdotgg#18442, and no release workflow sets VITE_HOSTED_APP_CHANNEL), ACP runtime instructions are one flag (sendRuntimeInstructions), the ACP adapter also resets unset options (pingdotgg#35199, held back on Buddy's instance too), provider hydration reads the database config (pingdotgg#34877), a natively resumed thread sends its unsent message (pingdotgg#36526), a failed send gives back the snapshot's draftText (pingdotgg#33124), a linked Environment's sender names it (pingdotgg#34721), an expandable work row's chevron sits between the acting-sender mark and the time (pingdotgg#35549), and the collapsed composer previews the prompt (pingdotgg#22148). Row 30's checks now pin that the one promote-to-steer is upstream's deferred steer, behind the pending-request guard that clears its steerWhenReadyRunId and steerWhenReadyIntent; the conditions under which an auto send in the gap becomes that steer, through resolveMessageDispatchIntent and the adapter's steering or interrupt-and-restart; and the delivery check that lets such a steer in only where the policy steers it then, by the session's capabilities. - v0.1.10 adds issue-vouch.yml (issues, push to main on VOUCHED.td) and pr-limits.yml (pull_request_target and a daily schedule at 05:23 UTC; it labels, comments on and closes pull requests, dry-run without PR_LIMITS_ENFORCE). Both run on ubuntu-24.04 in the fork too, so the swap step disables them right after the swap. The swap push itself starts issue-vouch.yml, since it adds the workflow and VOUCHED.td, so the step first cancels that run and then removes any vouch label it gave an open issue. - The Overlay table gains rows 35 to 37 for #214 and #216, and the Cílový stack names their commits on main and their files. Rows 4, 15, 21 and 30 record the fixes from the candidate's independent check (#222); the rest of the table is brought up to v0.1.10 after the release (stage 9). The runbook's "Z přestavby na v0.1.10" records the conflicts, the hand adaptations and those fixes, numbering rows as the table does, and names the replayed main (faae02a, stable 0.1.9-lazurio.2: 0.1.9-lazurio.1 at 388b772 with #214 and #216). - Main's #214, #216 and #220 additions to CI, the contract test and the runbook are carried unchanged; #216's narrow-rail pin follows row 36's `hidden` adaptation. A new contract pin holds row 35's hand-placed coordinator change: ThreadNotificationCoordinator.tsx reads hidden threads three times, always as listHiddenThreadKeysAtom, so Buddy's project's threads never sound, toast or notify. - The review of the candidate at 50a5004 (#222) adds to the runbook: the contract inventory names orchestrationV2.ts with steerWhenReadyIntent only; rows 24 and 30 record the recorded followWakes and the auto steer that a question puts first in the queue; the F50 gate names holders.vectors.test.ts and the vendored Platform v0.1.22 vectors; the check that ~/.local/bin/t3 points to the new version reads both forms of the launcher, a symlink and since v0.1.10 the script posixLauncherScript writes; and the update channel and its procedure describe the launcher protocol's move from 3 to 4, which an Update from 0.1.9 passes while the 0.1.9 launcher stays until a local update or service install restarts the service. The contract test pins the copied release and the vectors' runner. After the next review row 24 records the wait before the send, so a repeat racing the first send cannot record its own; the runbook says so and drops the crash between send and record from the known limits. After the review after that, T3 records the wait only until it accepts the key's command and each send reads the last record after it sent, so a send that fails between record and dispatch leaves no wait a retry follows; the contract test pins the record before the send, the read after it and the receipt check. After the review on c5cf16b, each keyed send claims its key before it sends and only the claim's holder sends, so the wait T3 keeps is the accepted send's; the runbook describes the claim, the send_in_progress refusal, CLAIM_TTL_MS and the limits, and the contract test pins the claim, the refusal, the release, the expiry and the receipt gate. After the review on 7b12202, only a send T3 refused before dispatching it releases its claim (UNSENT_FAILURES), and any other failure, such as a lost answer, keeps it until T3 accepts the command or CLAIM_TTL_MS passes; the runbook says so in the send-state paragraph and its limits, and the contract test pins the exact set. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Status: ready for review — do not merge before
v0.1.9-lazurio.1is tagged. This change goes into0.1.9-lazurio.2together with #214, in one preview round.What
In a narrow window (below 768 px, where T3's left panel is a modal sheet,
SIDEBAR_MOBILE_QUERY):min(88vw, 24rem), with no sliver of the conversation or the rail beside it. Its own toggle, or Escape, closes it and returns to the conversation.Until now it was the other way round: the rail stood beside the conversation and the open panel covered it.
How
The rail must be inside the dialog. T3's sheet is a modal Base UI dialog: it keeps the focus inside and marks everything outside
aria-hidden. A rail drawn beside it, as the first version of this PR did, was out of reach for the keyboard and screen readers.apps/web/index.htmlmoves the one<lazurio-rail>into the panel as its first child while the panel is on the page. Once the panel is gone it moves the rail back before#root, where the rail stays the target of the Environment jump.aria-hiddenbefore the move, the script drops that mark.body, gives the panel room for the rail, and keeps the sidebar wrapper contained while the rail is not#root's sibling. Without that containment, T3's fixed header controls showed above the panel.data-lazurio-dialog-open). The jump puts the focus into its search as it opens, so the script shows the rail already when the jump's key comes, in the window's capture phase, before the shell takes it. Once the key has passed, the rail settles: it hides again when the app took the key and no dialog opened.RightPanelSheet.tsx, the only sheet withoutdata-mobile. In the narrow block it getswidth: 100vw(andmin-width: 0,max-width: none, no start border, and the left safe area), scoped to a page with the shell. CSS only, and upstream's files are unchanged.sidebar.tsxandsheet.tsxare unchanged. The contract test guards the rule, the script and T3's breakpoint and sheet attributes. The runbook's "Lazurio shell" section describes the behaviour.Evidence
All captures were made on a test Environment as its owner persona, on the live 0.1.9 preview with exactly this CSS and script injected. Captures on the real build follow with the
0.1.9-lazurio.2preview.Right panel:
Keyboard at 390: the first Tab stop after opening the panel, and Enter on the rail's search.
Jump with the panel closed at 390: visible, focus in its search, typing works.
Recording at 390 (conversation → open the panel → the rail's search → Escape → conversation): https://gist.githubusercontent.com/immakermatty/a0551fe7ad78f06fbf07bc490b955bf1/raw/6fa92202927fd161130fc61ac123445dd55cf7da/390-video-po.mp4
Checks, in the same runs:
display: noneand the conversation spans the full width. With the panel open, the rail is the panel's child at x 0 and the panel's content starts after it. At 1440 nothing changes. There is no horizontal scroll at any width, and Buddy's launcher stays in its corner.aria-hiddenorinertancestor while the panel is open. Its accessibility tree reads navigation "Organizations" with its links and buttons, account included.body.openJump()right after it, as the key would reach them. In Chat today, T3 takes Ctrl/⌘+Shift+E outside the terminal, and the terminal takes it too, so the path is reached only with a changed binding.apps/web/src/lazurio/narrowRail.browser.test.tsxdrives T3's realSidebarat 390 px with index.html's own style and script and a stand-in rail. It checks the rail in four cases: the rail is hidden beside the conversation and is the first child of the open panel's dialog with noaria-hidden; the jump's key opens the jump visible, focused and typable; the rail stays hidden when the app takes the key; and the wide layout is unchanged. It also renders the realRightPanelSheet: full width at 390 with the shell, upstream's width at 900 and without the shell. Without the capture-phase reveal the jump test fails, and withoutwidth: 100vwthe right panel test fails.vp run check:changed: format, lint, knip, typecheck and tests pass.node --test scripts/lazurio-release-contract.test.mjs: 52 pass.Known, unchanged by this PR
composer.effort. The rail's jump shortcut therefore does not open there, with or without this change.Agent: environment a480495c-25e0-4e51-828b-1dbf1b77d62f · T3 thread b2963c0a-0588-4dde-8ece-390971647afc
🤖 Generated with Claude Code